Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Fix s3 session creation in deployment steps push_to_s3 and pull_from_s3 #322

Merged
merged 5 commits into from
Oct 11, 2023

Conversation

markbruning
Copy link
Contributor

@markbruning markbruning commented Oct 10, 2023

Closes #313

Example

When using an AwsCredentials block that has a profile name or other additional params, session creation will now work correctly.

Screenshots

N/A

Checklist

  • References any related issue by including "Closes #" or "Closes ".
    • If no issue exists and your change is not a small fix, please create an issue first.
  • Includes tests or only affects documentation.
  • Passes pre-commit checks.
    • Run pre-commit install && pre-commit run --all locally for formatting and linting.
  • Includes screenshots of documentation updates.
    • Run mkdocs serve view documentation locally.
  • Summarizes PR's changes in CHANGELOG.md

@markbruning markbruning requested a review from a team as a code owner October 10, 2023 19:05
@desertaxle
Copy link
Member

desertaxle commented Oct 10, 2023

Thanks for the PR @markbruning! Would you be able to add a test that uses the AwsCredentials block as an input like this:

get_s3_client(
    credentials=AwsCredentials(...).dict()
)

That will help us ensure the signature of get_s3_client stays compatible with AwsCredentials in its dict form.

Copy link
Member

@desertaxle desertaxle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

push_to_s3 and pull_from_s3 do not support additional AwsCredentials block parameters
2 participants